- 11 minutes to read

Manage Monitoring and Logging for Azure Logic Apps

Manage, monitor, and log your Azure Logic Apps with Nodinite, securely and without direct Azure Portal access.

What you will achieve with Nodinite:

✅ Secure, self-service management for business and IT users
✅ Advanced monitoring and logging for rapid troubleshooting
✅ Remote actions and configuration for streamlined operations
✅ Full audit trail for compliance and governance

Animated walkthrough: Disable a Logic App from the Action menu of a Monitor View, confirm with Yes, then Enable it again.

Application Management Team	IT Operations	Business
Let your AM team stop and start services independently	Stay in control with full access	Give your business Data and self-service for Logic Apps solutions

Features

The Nodinite Azure Logic Apps Logging and Monitoring Agent offers the following features:

Manage Monitoring thresholds
Manage Logging options
Perform Remote Actions
Remote Configuration

The Roles of your Users control access through Monitor Views and Log Views; see User access to logic apps monitoring and User access to logic apps logging.

Resource Name	Monitoring	Actions	Metrics/Statistics
Subscription	✅ Yes	Details	Statistics
Resource Group	✅ Yes	Details Inactivate	Statistics
Logic App	✅ Yes	Enable Disable Details Inactivate Edit Ignore evaluation errors View Run History View Trigger History	-
Failed Runs	✅ Yes	Manage Clear all failed runs	-
Failed Triggers	✅ Yes	Manage Clear all failed triggers	-
Log Configuration	✅ Yes	Details Diagnostics Settings	-

Info
All operations performed by you and other Users are logged to the Nodinite Audit Log, ensuring compliance with policies and regulations.

Remote Configuration

As an Administrator with access to Monitoring Agents, you can use the Remote Administration dialog to:

Add, Remove, and Manage Azure subscriptions
- Add, Remove, and Manage Resource groups within each subscription
Enable and Disable Monitoring
Enable and Disable Logging

See Configuration for details.

Azure Subscription

Tip
Manage the set of Resource Groups included in Logging and Monitoring from the Subscription Details page.

The 'Azure Subscription' Category provides a Resource for each configured Subscription, using the specified display name as the Resource name.
Example from a Monitor View with a configured Azure Subscription.

If you have permission to perform Remote Actions, the following operations are available:

The CONTROL CENTER part of the Action menu on a Subscription.

Subscription Details

To view and manage the selected Subscription Resource and its Resource Groups in Monitoring and Logging, click the Action button and select Details from the 'Control Center' menu.

The Details menu item opens the details modal for the selected Subscription.

Subscription details with the Resource Groups list and its Monitoring and Logging check boxes.

All available Resource Groups are listed (including those visible in Azure and those manually added in Configuration); the In Config/Azure column shows where each one comes from.

Monitoring is enabled for checked Resource Groups. Check or uncheck the row to enable or disable monitoring.
Logging can be enabled when Monitoring is enabled.

Tip
The list of Resource Groups can be filtered by typing in the filter text box.

Click Save to persist changes.
Save button used to persist subscription changes.

Subscription Statistics

To view statistics about Workflows in the selected Subscription Resource, click the Action button and select Statistics from the 'Control Center' menu.

The Statistics menu item opens the Statistics modal for the selected Subscription.

Statistics modal for the selected Subscription.

All Workflows in the Resource Groups for the current Configuration are shown in accordions.

Statistics table

The table lists Workflows and provides valuable details:

KPI	Description
Max invocations	The Workflow Run with the most Action Invocations. This helps identify Workflows with excessive loops. For Consumption-based Workflows, this can indicate high costs.
Total invocations	Total number of Action Invocations. A large number may indicate a costly or resource-intensive Workflow.
Succeeded	Total number of successful runs.
Failures	Total number of failed runs.
Max Duration	Duration of the slowest run.
Min Duration	Duration of the fastest run.
Avg Duration	Average duration for all runs.
First run	Date of the oldest Workflow run.
Last run	Date of the most recent Workflow run.

Resource Group

The Category 'Resource Group' provides a Resource for each Resource Group included in Monitoring.
Example of a filtered Monitor View with the Resource Group Category.

If you have permission to perform Remote Actions, the following operations are available:

The CONTROL CENTER part of the Action menu on a Resource Group.

Resource Group Details

To view the selected Resource Group Resource, click the Action button and select Details from the 'Control Center' menu.

The Details menu item opens the details modal for the selected Resource Group.

Details modal for a Resource Group, with its Logic Apps, their Diagnostics state, and Event Hubs.

Info
The data is logically the same for Logic Apps Standard and Consumption.

Inactivate Resource Group

If a Resource Group no longer exists in Azure, select Inactivate in the Action menu to remove it from Monitoring and Logging. You can open the Details page even for unavailable Resource Groups.
The Inactivate menu item on a Resource Group.

Execute action? asks you to confirm with Yes or abort with No.

Example of an Inactive Success Resource Group.

Resource Group Statistics

To view statistics about Workflows in the selected Resource Group Resource, click the Action button and select Statistics from the 'Control Center' menu.

The Statistics menu item opens the Statistics modal for the selected Resource Group.

The Azure Workflows Statistics table lists each Logic App in the Resource Group.

See the Statistics table for the columns.

Logic App

The Category 'Logic App' provides a resource for each Logic App found in configured Azure Subscriptions.
Example from a Monitor View with Logic Apps included in Monitoring.

Info
See Monitoring Logic Apps for more details about Logic Apps Monitoring.

The following Remote Actions are available on Logic Apps in Monitor Views that allow Remote Actions. Disable, Enable, Ignore evaluation errors, and Inactivate change something, so each first asks Execute action?; answer Yes to run it or No to abort.

The CONTROL CENTER part of the Action menu on a Logic App.

Logic App Details

To get details about a Workflow, click the Action button and select Details.

The Details menu item on a Logic App.

Details for a Workflow: Resource group, Subscription, Is Consumption, and Monitoring (Global or specific thresholds).

Note
Review the Diagnostic settings to ensure the agent configuration matches Azure and that Monitoring and Logging are operational.

Disable Logic App

To change the state of an enabled Logic App, click the Action button and select Disable.

The Disable menu item on a Logic App.

In the dialog, confirm or abort the action.

Execute action? names the action and the Logic App.

The outcome of the operation is then displayed.

Success: the Logic App is now disabled.

Edit thresholds Logic App

To change Monitoring thresholds, select Edit in the Action menu. It opens the Edit Monitoring thresholds modal.

The Edit menu item on a Logic App.

The Properties section of the modal lets you manage:

Field	Description
Description	A user-friendly description of the Workflow.
Last clear date time	Ignore execution errors before this time.

Top part of Edit Monitoring thresholds: Properties and the start of Thresholds.

The Thresholds section sets non-event Monitoring thresholds that override the global thresholds.

Bottom part: the remaining thresholds and Save.

Use global thresholds – When checked, the Workflow uses the global settings
Lookback period – From 5 minutes to 4 weeks; how far back in time to look, used when the current time is past the last clear date-time plus the lookback period
⚠️ Warning and ❌ Error values for Min execution count, Max execution count, and Max invocation count (-1 disables the check, the default), and for Duration (ms)

Enable Logic App

To change the state of a disabled Logic App, click the Action button and select Enable.

The Enable menu item on a Logic App.

Confirm or abort the operation in the dialog.
Execute action? names the action and the Logic App.

The outcome of the operation is then displayed.
Success: the Logic App is now enabled.

Ignore Evaluation Errors

The Ignore evaluation errors menu item on a Logic App; it asks Execute action? before it runs.

Inactivate Logic App

When a Workflow is removed in Azure, Nodinite reports it as 🚫 Unavailable. Nodinite cannot tell whether the removal was intentional, so an Administrator must click Inactivate to stop monitoring it.

Important
Why Inactivate and NOT Exclude? With an exclusion, the agent keeps querying the Azure REST API for a Workflow that no longer exists, wasting API calls and bandwidth. Inactivate stops those calls.

Info
If the Workflow is redeployed, it will be detected and automatically reappear in Monitoring.

The Inactivate menu item on a Logic App.

In the dialog, confirm or abort the action.
Execute action? names the action and the Logic App.

The outcome of the operation is then displayed.
Result from operation.

Warning
You cannot remove a Workflow if the system still believes it is present.

View Logic App Run History

To view Workflow run history, select View Run History in the Action menu. It shows what Azure still keeps; see Reduce Azure Logic Apps Run History Retention to Lower TCO. The walkthrough is on Monitoring Logic Apps.

The View Run History menu item on a Logic App.

The Runs history modal filters by status (Aborted to Waiting) and time span, and Sync reads the latest runs from Azure into the agent; nothing is written to Azure. From any row, you can open the run in Azure or, as an Administrator, open its Trigger and Action events through the Correlation Id link, according to your current Log Configuration.
A run with its identifier, duration, and Correlation Id.

View Logic App Trigger History

View Trigger History opens the Triggers history modal, with the same status and time span filters and Sync.
The Triggers history modal for a Logic App.

Failed Runs

If there are failed runs newer than the last Clear DateTime, the Logic App is listed with the ❌ Error Monitoring state, and Alarm Plugins notify the subscribers of the Monitor View. You can see the full list of failed runs since the last clear date.

For each Workflow, there is a Category 'Failed Runs'.
Example from a Nodinite Monitor View with a Logic App in the Failed Runs Category.

The Remote Actions Manage and Clear all failed runs are on this Resource; see Managing Failed Runs for both, with a walkthrough.

The CONTROL CENTER part of the Action menu on a Failed Runs Resource.

Failed Triggers

For each Workflow, the 'Failed Triggers' Category lists failed triggers, with the Remote Actions Manage and Clear all failed triggers, like Failed Runs.
The Manage Failed Triggers modal with the Clear all Failed Triggers button.

Log Configuration

Each Subscription has one Log Configuration Resource. This Resource is part of Monitoring and any detected problem is presented accordingly.
Example of the Log Configuration Resource.

You can use the following Remote Actions to interact with the current Log Configuration:

The CONTROL CENTER part of the Action menu on the Log Configuration Resource.

Log Configuration Details

To view details for the current Log Configuration on the selected Subscription, click the Action button and select Details.
The Details menu item on the Log Configuration.

The header shows the Subscription, LogApi is alive, Logging is enabled, and the Log Agent Value Id. Expand Diagnostic Settings for the setting per Logic App and Event Hub Configuration for the Event Hub and its checkpoint container.
Details about the current Log Configuration: two Logic Apps send to one Event Hub.

To add or update Diagnostics settings, click the Action button on the Log Configuration Resource and select Diagnostics Settings.

The Diagnostics Settings menu item opens Create Or Update Diagnostic settings.

To apply the same diagnostic setting to many Workflows, use an ARM Template instead; About Logic Apps Logging options explains which categories to enable.

The modal that creates or updates a diagnostic setting in Azure for Logging and Monitoring with Nodinite.

Name – The name of the diagnostics setting
SAS Policy ARM ID – The resource ID for a SAS Policy to access the Event Hub
Field used to enter the SAS Policy ARM ID required for Azure Event Hub access.
Logic Apps
- Either the Logic App Standard service plan, or (applies to ALL Workflows in this instance)
- Individual Consumption-based Workflow
Event Hub Name – The target entity name of the Event Hub for Azure Diagnostics

Note
You must configure the Nodinite Azure Logic Apps Logging and Monitoring Agent and match the Azure diagnostics configuration with the listener (this agent).

Frequently asked questions

See the Troubleshooting user guide for solutions to common problems and the FAQ.

Note
To manage your Logic Apps from Nodinite, you must enable Monitoring of Logic Apps, as described in the configuration page

Next Steps

Configure Message Types - Make your Logic Apps data searchable and enable advanced features
Managing Failed Runs - Resubmit, clear, and trace failed runs
User access to logic apps monitoring - Give teams self-service through Monitor Views

Azure Logic Apps Overview
Message Types - Critical for Search Field extraction from Logic Apps events
Search Fields - Extract business data from Logic Apps messages
Non-Events Monitoring - Track message volumes and patterns
BPM - End-to-end process tracking across Logic Apps and other systems

Explore Nodinite for 30 days – completely free

See how Nodinite resolves your technical issues, in a

LIVE Demo!